entitys icon

entitys

entitys.io: Import (webhook trigger) or Export (HTTP POST).

Export

AI-generated

Overview

This node provides two main operations: Import and Export. The Export operation sends data via an HTTP POST request to a specified URL with a customizable JSON payload and optional additional headers. This is useful for integrating workflows with external APIs or services that accept data through POST requests.

Common scenarios include:

  • Sending processed data from n8n workflows to third-party APIs.
  • Triggering external systems by posting JSON-formatted events or commands.
  • Automating data export tasks where the target system requires HTTP POST communication.

For example, you might use this node to send order details to a remote inventory management system or post user registration data to a CRM platform.

Properties

Name Meaning
URL The endpoint URL to which the HTTP POST request will be sent.
JSON Body The JSON payload to include in the body of the POST request.
Additional Headers Optional HTTP headers to add to the request. You can specify multiple headers as name-value pairs.

Output

The node outputs an array with one item containing a json object structured as follows:

  • statusCode: The HTTP status code returned by the POST request.
  • headers: The HTTP response headers received from the server.
  • body: The parsed JSON response body from the server.

This output allows subsequent nodes to handle the response data, check for success or failure, and process any returned information.

Dependencies

  • Requires an active internet connection to reach the specified URL.
  • No special API key or authentication mechanism is built-in; if needed, users must provide appropriate headers (e.g., Authorization) via the "Additional Headers" property.
  • Uses n8n's built-in HTTP request helper to perform the POST request.

Troubleshooting

  • Invalid JSON Body: If the JSON Body input is not valid JSON, the node throws an error indicating "Invalid JSON Body". Ensure the JSON syntax is correct.
  • HTTP Errors: If the target URL is unreachable or returns an error status code, the node still outputs the response but users should check the statusCode and body fields to diagnose issues.
  • Missing URL: The URL property is required; leaving it empty will cause the node to fail.
  • Headers Format: Additional headers must be provided as name-value pairs; incorrect formatting may lead to unexpected request behavior.

Links and References

Discussion